Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a72818aaecb654816e5b5c1471fb1f49b4af89ab061d513d18c8c55364a1645

Tx prefix hash: ec7711c34cb4d37e858d0eae988d2e44ce122d7323b3da2a1114d62bf5e3b708
Tx public key: e4f22e12e56a4b9ba1e67f39e8599a2a207abd1133d49aea22032c5b8d06a52d
Timestamp: 1710938736 Timestamp [UCT]: 2024-03-20 12:45:36 Age [y:d:h:m:s]: 00:298:12:52:55
Block: 982458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213669 RingCT/type: yes/0
Extra: 01e4f22e12e56a4b9ba1e67f39e8599a2a207abd1133d49aea22032c5b8d06a52d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c73413ae0ed15ef4a32c14e16f37e6002e462da597003ded036ce1ef8c9654 0.600000000000 1442563 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": 982468, "vin": [ { "gen": { "height": 982458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c73413ae0ed15ef4a32c14e16f37e6002e462da597003ded036ce1ef8c9654" } } ], "extra": [ 1, 228, 242, 46, 18, 229, 106, 75, 155, 161, 230, 127, 57, 232, 89, 154, 42, 32, 122, 189, 17, 51, 212, 154, 234, 34, 3, 44, 91, 141, 6, 165, 45, 2, 17, 0, 0, 0, 1, 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