Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055599aa64cedde277fab0794bdc18f64d0a2a06fb010df988dccac46057c887

Tx prefix hash: 3b08e41c690fc6c5f394f54b2e623d91f8e7b84c7c01b8c893156b8b08f8903c
Tx public key: 4494286555ce68d9b1a48aff32f86e29ba220d27332d7c1d51210d4df5f758a5
Timestamp: 1731610220 Timestamp [UCT]: 2024-11-14 18:50:20 Age [y:d:h:m:s]: 00:125:04:45:40
Block: 1153717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89320 RingCT/type: yes/0
Extra: 014494286555ce68d9b1a48aff32f86e29ba220d27332d7c1d51210d4df5f758a50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fbec3f090025db98370605d85894daa4e7d8f1420e7fd6f35ef639c5dd93712 0.600000000000 1639328 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": 1153727, "vin": [ { "gen": { "height": 1153717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fbec3f090025db98370605d85894daa4e7d8f1420e7fd6f35ef639c5dd93712" } } ], "extra": [ 1, 68, 148, 40, 101, 85, 206, 104, 217, 177, 164, 138, 255, 50, 248, 110, 41, 186, 34, 13, 39, 51, 45, 124, 29, 81, 33, 13, 77, 245, 247, 88, 165, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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