Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e813ae2906f84cfa2a05481bcce4fb2b9ac13148e5709d8a5c8534a6cbfdfe8

Tx prefix hash: e3bc4916a8a2966165bf97bb379db3469bf5e5ddc15dd4fb159030af4a8e6ee6
Tx public key: 078a0accae96f51d7dd7dfe7f1aeb656d00fd8b46d56be7e162e983dcdb32336
Timestamp: 1649317795 Timestamp [UCT]: 2022-04-07 07:49:55 Age [y:d:h:m:s]: 02:237:13:13:56
Block: 474977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689542 RingCT/type: yes/0
Extra: 01078a0accae96f51d7dd7dfe7f1aeb656d00fd8b46d56be7e162e983dcdb3233602110000000e4da16a3a000000000000000000

1 output(s) for total of 16.375865733000 dcy

stealth address amount amount idx
00: f11d74df322253998d31b5fb612947e53a84c61b5a5d40ad71b3eb668462b844 16.375865733000 895134 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": 474987, "vin": [ { "gen": { "height": 474977 } } ], "vout": [ { "amount": 16375865733, "target": { "key": "f11d74df322253998d31b5fb612947e53a84c61b5a5d40ad71b3eb668462b844" } } ], "extra": [ 1, 7, 138, 10, 204, 174, 150, 245, 29, 125, 215, 223, 231, 241, 174, 182, 86, 208, 15, 216, 180, 109, 86, 190, 126, 22, 46, 152, 61, 205, 179, 35, 54, 2, 17, 0, 0, 0, 14, 77, 161, 106, 58, 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