Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4afdb16b7481d02d5913dfc150bcea7e1482c6a66cc1e6336f9056a3b69b7e9d

Tx prefix hash: cc30f750be2551da315b9eb68b201fb68212f0aef7532d2b7cdbdc4a2ab498d5
Tx public key: 817266cbff2d9613e2b1d8ce18cdd41fa1787008f1dba9a1087564d653d388b8
Timestamp: 1719533408 Timestamp [UCT]: 2024-06-28 00:10:08 Age [y:d:h:m:s]: 00:178:06:26:50
Block: 1053684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127609 RingCT/type: yes/0
Extra: 01817266cbff2d9613e2b1d8ce18cdd41fa1787008f1dba9a1087564d653d388b80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8ac0e6f692ecc935a858e07a90c05b09222101ba6eb6daee1a77135658cf5e5 0.600000000000 1524031 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": 1053694, "vin": [ { "gen": { "height": 1053684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8ac0e6f692ecc935a858e07a90c05b09222101ba6eb6daee1a77135658cf5e5" } } ], "extra": [ 1, 129, 114, 102, 203, 255, 45, 150, 19, 226, 177, 216, 206, 24, 205, 212, 31, 161, 120, 112, 8, 241, 219, 169, 161, 8, 117, 100, 214, 83, 211, 136, 184, 2, 17, 0, 0, 0, 1, 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