Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0c77ddb093895bc39b23928d4697ca38e061c58d7d37e48c13bf942726e8a9

Tx prefix hash: 1b5978086ac58c82af948f046c7b509419cc62a9748acf99b36b999b49ae8367
Tx public key: 12f7c4ffe9044c666a0c889c83cacd0ef2297df86aa273912573b4cae7370044
Timestamp: 1728245344 Timestamp [UCT]: 2024-10-06 20:09:04 Age [y:d:h:m:s]: 00:109:15:11:24
Block: 1125910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78332 RingCT/type: yes/0
Extra: 0112f7c4ffe9044c666a0c889c83cacd0ef2297df86aa273912573b4cae737004402110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f6d3ee14f7b6bc536080b9fa5974206c8dcfd2dfd9c8dd3f49e5b2d8eb8e3c3 0.600000000000 1608683 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": 1125920, "vin": [ { "gen": { "height": 1125910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f6d3ee14f7b6bc536080b9fa5974206c8dcfd2dfd9c8dd3f49e5b2d8eb8e3c3" } } ], "extra": [ 1, 18, 247, 196, 255, 233, 4, 76, 102, 106, 12, 136, 156, 131, 202, 205, 14, 242, 41, 125, 248, 106, 162, 115, 145, 37, 115, 180, 202, 231, 55, 0, 68, 2, 17, 0, 0, 0, 11, 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