Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99827f8c74b7066831e8b80f7343544ee5f2f422ac357a83ef2f164e6850c6e7

Tx prefix hash: 4489cef3352fe193ef665bc45a8144f2fd21a65d8b5e4384c44cbf42bdc95d41
Tx public key: 7213ca1cae55cb9885df6583cc3a530f20deb93c98aecc9d365bd945c526c273
Timestamp: 1748546129 Timestamp [UCT]: 2025-05-29 19:15:29 Age [y:d:h:m:s]: 00:175:20:40:56
Block: 1293679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123364 RingCT/type: yes/0
Extra: 017213ca1cae55cb9885df6583cc3a530f20deb93c98aecc9d365bd945c526c27302110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b515afbf27ebc42c66d6b9826b8b880bdbdf65e138daeb5a7ef0d5512ef1b1e 0.600000000000 1781166 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": 1293689, "vin": [ { "gen": { "height": 1293679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b515afbf27ebc42c66d6b9826b8b880bdbdf65e138daeb5a7ef0d5512ef1b1e" } } ], "extra": [ 1, 114, 19, 202, 28, 174, 85, 203, 152, 133, 223, 101, 131, 204, 58, 83, 15, 32, 222, 185, 60, 152, 174, 204, 157, 54, 91, 217, 69, 197, 38, 194, 115, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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