Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b53e3e8588dc4e3bd496cbee2a8c4452704a803cf0d5917dbac9e14c2b6facf8

Tx prefix hash: 2aecbdd7f549d611d32b87222afb373ced2b1c4e691114e31b77f81f89546d44
Tx public key: 3f85f382426fb16511493061e1c79c6f322cb505d28ea80636f3868b43368d63
Timestamp: 1577617446 Timestamp [UCT]: 2019-12-29 11:04:06 Age [y:d:h:m:s]: 04:333:12:38:38
Block: 34314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127419 RingCT/type: yes/0
Extra: 013f85f382426fb16511493061e1c79c6f322cb505d28ea80636f3868b43368d63021100000002d81c26c0000000000000000000

1 output(s) for total of 472.393952854000 dcy

stealth address amount amount idx
00: a5c3971b4c04203da0832f4721442b21c8a66abfdf4dee8d4b8b69c694bfdd8e 472.393952854000 57713 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": 34324, "vin": [ { "gen": { "height": 34314 } } ], "vout": [ { "amount": 472393952854, "target": { "key": "a5c3971b4c04203da0832f4721442b21c8a66abfdf4dee8d4b8b69c694bfdd8e" } } ], "extra": [ 1, 63, 133, 243, 130, 66, 111, 177, 101, 17, 73, 48, 97, 225, 199, 156, 111, 50, 44, 181, 5, 210, 142, 168, 6, 54, 243, 134, 139, 67, 54, 141, 99, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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