Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a6dd7cdff6c188ef00873d43604fb7fa0404d45efcc43b09c12530c72038ae

Tx prefix hash: 1a4e6895cb28b8ce036c6ee9d5876ae6d64e9d13bb955c369918181b73ff8f44
Tx public key: 419dd7d30571d064d2309118f60f17119f6e8ee2f90c9c53c79a1e7bc02a881d
Timestamp: 1735946512 Timestamp [UCT]: 2025-01-03 23:21:52 Age [y:d:h:m:s]: 00:166:14:17:57
Block: 1189631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118768 RingCT/type: yes/0
Extra: 01419dd7d30571d064d2309118f60f17119f6e8ee2f90c9c53c79a1e7bc02a881d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9c29ddc5c2f579bc0ed800c461394ee95363a4c9a52edf8bc6a38600a152e2 0.600000000000 1676142 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": 1189641, "vin": [ { "gen": { "height": 1189631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9c29ddc5c2f579bc0ed800c461394ee95363a4c9a52edf8bc6a38600a152e2" } } ], "extra": [ 1, 65, 157, 215, 211, 5, 113, 208, 100, 210, 48, 145, 24, 246, 15, 23, 17, 159, 110, 142, 226, 249, 12, 156, 83, 199, 154, 30, 123, 192, 42, 136, 29, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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