Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b0d04a495247cc986f0c05edbc8b288e2e07cf04eb9e08c8f49045eedd3dbcfb

Tx prefix hash: 08d9dd0320039d4a2e20c37bb132215b81783c5b4b87363113e4f0fea14489b8
Tx public key: 2803993ce90a12cd471ad39869f18092c9a67447cf3f26d2baa2428c33f2f2db
Timestamp: 1577907402 Timestamp [UCT]: 2020-01-01 19:36:42 Age [y:d:h:m:s]: 04:362:21:28:53
Block: 36565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148583 RingCT/type: yes/0
Extra: 012803993ce90a12cd471ad39869f18092c9a67447cf3f26d2baa2428c33f2f2db0211000001034fb58672000000000000000000

1 output(s) for total of 464.350405153000 dcy

stealth address amount amount idx
00: c9ea2a5431c25fdce0368c38a232849b68c1a0071fa406651d1a7a8c536ba0f7 464.350405153000 61962 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 36575, "vin": [ { "gen": { "height": 36565 } } ], "vout": [ { "amount": 464350405153, "target": { "key": "c9ea2a5431c25fdce0368c38a232849b68c1a0071fa406651d1a7a8c536ba0f7" } } ], "extra": [ 1, 40, 3, 153, 60, 233, 10, 18, 205, 71, 26, 211, 152, 105, 241, 128, 146, 201, 166, 116, 71, 207, 63, 38, 210, 186, 162, 66, 140, 51, 242, 242, 219, 2, 17, 0, 0, 1, 3, 79, 181, 134, 114, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8