Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1bb23994d7467230be47b317c15189d7f86d5ef91015503b05240a7a4551e1

Tx prefix hash: a675a967dcf62cd28a53cf8390f97784a4594a1bdad88bd5cf6ef8d33e9ddf75
Tx public key: 6985ff5cf9cd0d5d9f6a17a01c4f9ff09a7dc49676f87edfbfcfc94e918289e0
Timestamp: 1593017544 Timestamp [UCT]: 2020-06-24 16:52:24 Age [y:d:h:m:s]: 04:155:07:23:21
Block: 110446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1051301 RingCT/type: yes/0
Extra: 016985ff5cf9cd0d5d9f6a17a01c4f9ff09a7dc49676f87edfbfcfc94e918289e002110000001846a11e8a000000000000000000

1 output(s) for total of 264.269657027000 dcy

stealth address amount amount idx
00: 4fa5089e64341655931622edfb2b851bf4f58af2d25977857598959d374b26bf 264.269657027000 191330 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": 110456, "vin": [ { "gen": { "height": 110446 } } ], "vout": [ { "amount": 264269657027, "target": { "key": "4fa5089e64341655931622edfb2b851bf4f58af2d25977857598959d374b26bf" } } ], "extra": [ 1, 105, 133, 255, 92, 249, 205, 13, 93, 159, 106, 23, 160, 28, 79, 159, 240, 154, 125, 196, 150, 118, 248, 126, 223, 191, 207, 201, 78, 145, 130, 137, 224, 2, 17, 0, 0, 0, 24, 70, 161, 30, 138, 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