Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5753280b150d2a7816ab2ac4f995e195440d6c51b4ce793350f1f6814a655553

Tx prefix hash: 966876fd1f39a38b5ac0dffc6848c00753053a0ed9877da6a494555e7abe9d8c
Tx public key: 85867071cd639f5d0cead78f56d36b5578aeb7c8bb813f3c2785f1e176ff4d2a
Timestamp: 1711742326 Timestamp [UCT]: 2024-03-29 19:58:46 Age [y:d:h:m:s]: 00:334:19:58:23
Block: 989116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239357 RingCT/type: yes/0
Extra: 0185867071cd639f5d0cead78f56d36b5578aeb7c8bb813f3c2785f1e176ff4d2a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b890d3f31fb9a8c7c7ccb05233d3069b7d434dd1de291b50491d82e8dc187d 0.600000000000 1449411 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": 989126, "vin": [ { "gen": { "height": 989116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b890d3f31fb9a8c7c7ccb05233d3069b7d434dd1de291b50491d82e8dc187d" } } ], "extra": [ 1, 133, 134, 112, 113, 205, 99, 159, 93, 12, 234, 215, 143, 86, 211, 107, 85, 120, 174, 183, 200, 187, 129, 63, 60, 39, 133, 241, 225, 118, 255, 77, 42, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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