Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a787552da88964e0a4261d28c5ebfddd0743593debe65e6a8d7765f00f9c5ff9

Tx prefix hash: 87ab794e63d314fd81eda0cc6dbdac808b826d6944f1289d61117a205de55908
Tx public key: 570bcb29c6b20e7ec48672b54771333f0ab35370a885098f91d03950fdc0e00f
Timestamp: 1696092999 Timestamp [UCT]: 2023-09-30 16:56:39 Age [y:d:h:m:s]: 01:254:08:58:57
Block: 859557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442887 RingCT/type: yes/0
Extra: 01570bcb29c6b20e7ec48672b54771333f0ab35370a885098f91d03950fdc0e00f02110000000333af99f4000000000000000000

1 output(s) for total of 0.870824988000 dcy

stealth address amount amount idx
00: d72b1cee3e0a7b09ae7cf10a2d55eba1a9d7ac4b6331b48bdbfeacdf83e13852 0.870824988000 1313789 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": 859567, "vin": [ { "gen": { "height": 859557 } } ], "vout": [ { "amount": 870824988, "target": { "key": "d72b1cee3e0a7b09ae7cf10a2d55eba1a9d7ac4b6331b48bdbfeacdf83e13852" } } ], "extra": [ 1, 87, 11, 203, 41, 198, 178, 14, 126, 196, 134, 114, 181, 71, 113, 51, 63, 10, 179, 83, 112, 168, 133, 9, 143, 145, 208, 57, 80, 253, 192, 224, 15, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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