Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d033bf5d15479d39813879a8b702cc81fcc88e472c839a2579803433558e6d

Tx prefix hash: 3a88583820385b0e376826a6dc5da1453eb62cb7cfb6d3c3a6001dc237e97e7c
Tx public key: c7a2442ff5688cb02c86aba5afb29d4091f34e6e07920a8e5ea03dba50eee619
Timestamp: 1711733086 Timestamp [UCT]: 2024-03-29 17:24:46 Age [y:d:h:m:s]: 00:299:16:19:52
Block: 989036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214441 RingCT/type: yes/0
Extra: 01c7a2442ff5688cb02c86aba5afb29d4091f34e6e07920a8e5ea03dba50eee6190211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2793beb999ed970da5e668e4f22a6b456f86e8dab288d290f6b0ff9a7bb9319e 0.600000000000 1449329 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": 989046, "vin": [ { "gen": { "height": 989036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2793beb999ed970da5e668e4f22a6b456f86e8dab288d290f6b0ff9a7bb9319e" } } ], "extra": [ 1, 199, 162, 68, 47, 245, 104, 140, 176, 44, 134, 171, 165, 175, 178, 157, 64, 145, 243, 78, 110, 7, 146, 10, 142, 94, 160, 61, 186, 80, 238, 230, 25, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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