Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be844d5384a4b09a36361cd65280375f8f1045cb33e3368f36111e26939d1fe

Tx prefix hash: e603063af2ca0a6554019f51e6a79bd7886fb1e97e5c577c67988843f5942f5e
Tx public key: 97a896f5a178381143d1c18ebd0ebf78a499e33fb4ea098f5eb403bf68a45553
Timestamp: 1713223886 Timestamp [UCT]: 2024-04-15 23:31:26 Age [y:d:h:m:s]: 01:222:18:35:11
Block: 1001360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417914 RingCT/type: yes/0
Extra: 0197a896f5a178381143d1c18ebd0ebf78a499e33fb4ea098f5eb403bf68a455530211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2785b5441e0318264a680c99fd8b54e5e619d5f34624fc319a4e4e5836931696 0.600000000000 1461864 of 15

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": 1001370, "vin": [ { "gen": { "height": 1001360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2785b5441e0318264a680c99fd8b54e5e619d5f34624fc319a4e4e5836931696" } } ], "extra": [ 1, 151, 168, 150, 245, 161, 120, 56, 17, 67, 209, 193, 142, 189, 14, 191, 120, 164, 153, 227, 63, 180, 234, 9, 143, 94, 180, 3, 191, 104, 164, 85, 83, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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