Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba580925fe1571b8a845937c0c7267b2d44720e804002bec4644aec6aec61bdb

Tx prefix hash: 901fdc1f964a2adc1dade8cad33a47faf3194d6eec4495efab759a41cf6fae79
Tx public key: 8bc5acfedfe490310a3f9e473ef9deec4a68c6d131f16e14f2b953e8bb49d685
Timestamp: 1737604320 Timestamp [UCT]: 2025-01-23 03:52:00 Age [y:d:h:m:s]: 00:147:09:35:36
Block: 1203309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105084 RingCT/type: yes/0
Extra: 018bc5acfedfe490310a3f9e473ef9deec4a68c6d131f16e14f2b953e8bb49d685021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c28d4b5ada9241a887d9906b5d5279ef1df4e7bc0a4baef396f2a83fc9bf417e 0.600000000000 1689984 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": 1203319, "vin": [ { "gen": { "height": 1203309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c28d4b5ada9241a887d9906b5d5279ef1df4e7bc0a4baef396f2a83fc9bf417e" } } ], "extra": [ 1, 139, 197, 172, 254, 223, 228, 144, 49, 10, 63, 158, 71, 62, 249, 222, 236, 74, 104, 198, 209, 49, 241, 110, 20, 242, 185, 83, 232, 187, 73, 214, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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