Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469040246cb6be9cd54471b76cfac00ee06bdfc1853c1b4f1ae25704c2c515e4

Tx prefix hash: 0bb8080a85d39e8a569a1d7d6d91b4b44bdb5c818c1d2f684999b80d83e25f8e
Tx public key: fd6e14ecda2298c8063f417736757fa76e0da5c984773c329e9d405792c4eccf
Timestamp: 1736144307 Timestamp [UCT]: 2025-01-06 06:18:27 Age [y:d:h:m:s]: 00:100:07:06:03
Block: 1191282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71457 RingCT/type: yes/0
Extra: 01fd6e14ecda2298c8063f417736757fa76e0da5c984773c329e9d405792c4eccf02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6738333b6372c13700d099c90699db2a06fc0bacd49683587ccf07fba23cbfc 0.600000000000 1677807 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": 1191292, "vin": [ { "gen": { "height": 1191282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6738333b6372c13700d099c90699db2a06fc0bacd49683587ccf07fba23cbfc" } } ], "extra": [ 1, 253, 110, 20, 236, 218, 34, 152, 200, 6, 63, 65, 119, 54, 117, 127, 167, 110, 13, 165, 201, 132, 119, 60, 50, 158, 157, 64, 87, 146, 196, 236, 207, 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