Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243ecebee777808575dbf233ebeb381b941bbac63b401171232de4451ad5739d

Tx prefix hash: 401973cc9faf2d008c739d331d3f7050daec0a24312aebf34fafadc84db1de63
Tx public key: 785f164c377cb4f0b140c1f3c0c0a4f8b189dfa26f1d49b0dabd1d5a1104716f
Timestamp: 1741407058 Timestamp [UCT]: 2025-03-08 04:10:58 Age [y:d:h:m:s]: 00:257:18:16:22
Block: 1234568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181962 RingCT/type: yes/0
Extra: 01785f164c377cb4f0b140c1f3c0c0a4f8b189dfa26f1d49b0dabd1d5a1104716f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600120000000 dcy

stealth address amount amount idx
00: fd594f8aca3fd0b6a70a68fe49867a348c8bb768f9ed625d06fd175a5faa2c03 0.600120000000 1721497 of 0

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": 1234578, "vin": [ { "gen": { "height": 1234568 } } ], "vout": [ { "amount": 600120000, "target": { "key": "fd594f8aca3fd0b6a70a68fe49867a348c8bb768f9ed625d06fd175a5faa2c03" } } ], "extra": [ 1, 120, 95, 22, 76, 55, 124, 180, 240, 177, 64, 193, 243, 192, 192, 164, 248, 177, 137, 223, 162, 111, 29, 73, 176, 218, 189, 29, 90, 17, 4, 113, 111, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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