Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d44647d98507bdf035069144d0ea7c55db415c43509279681b6079af2621eb2

Tx prefix hash: cf8f20c2ea17df6b8aa08b96aa0070d4ad70cc57993fa2ca8f1d0d085c147495
Tx public key: 7a4b0be9a67d0c40e6de8346b7c839fca9ae97b4c5311e419d34fa43f34dbd68
Timestamp: 1718751852 Timestamp [UCT]: 2024-06-18 23:04:12 Age [y:d:h:m:s]: 00:295:19:15:11
Block: 1047211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211378 RingCT/type: yes/0
Extra: 017a4b0be9a67d0c40e6de8346b7c839fca9ae97b4c5311e419d34fa43f34dbd6802110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4f78b82c9ee69a93b4f02c26fea6065058ae6f63da34e4f49f1642424771115 0.600000000000 1517030 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": 1047221, "vin": [ { "gen": { "height": 1047211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4f78b82c9ee69a93b4f02c26fea6065058ae6f63da34e4f49f1642424771115" } } ], "extra": [ 1, 122, 75, 11, 233, 166, 125, 12, 64, 230, 222, 131, 70, 183, 200, 57, 252, 169, 174, 151, 180, 197, 49, 30, 65, 157, 52, 250, 67, 243, 77, 189, 104, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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