Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dd9a0996cc0b67379c0ddb25acf7ca55af76a4893d24f11489d7e091438588b

Tx prefix hash: 2961262286fd505475493fbebf653377aea6bfd47f2151e073d40f0fa7048d42
Tx public key: a63349aea9546c4ec027dfb533ea2ee304179de526b023c8a04c1021ebc0f997
Timestamp: 1722713841 Timestamp [UCT]: 2024-08-03 19:37:21 Age [y:d:h:m:s]: 00:296:23:05:13
Block: 1080043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212182 RingCT/type: yes/0
Extra: 01a63349aea9546c4ec027dfb533ea2ee304179de526b023c8a04c1021ebc0f99702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df638dcbef5d71a56ab1284c160be661f5ba2f4271b88086d99e742a865f4fb8 0.600000000000 1553252 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": 1080053, "vin": [ { "gen": { "height": 1080043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df638dcbef5d71a56ab1284c160be661f5ba2f4271b88086d99e742a865f4fb8" } } ], "extra": [ 1, 166, 51, 73, 174, 169, 84, 108, 78, 192, 39, 223, 181, 51, 234, 46, 227, 4, 23, 157, 229, 38, 176, 35, 200, 160, 76, 16, 33, 235, 192, 249, 151, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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