Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac562fafd45ad148e72e41ac09c5c067e4186e31cf48b6ab72ad2a63c0cee29a

Tx prefix hash: 3e72723e0462034041adb81804b4bdb6fa89f9c20600661658d599c6cc29c031
Tx public key: b02e06e66fc4de6e0bd18540a5c403353b8db6c7e543ce07486b0374e8365659
Timestamp: 1695268810 Timestamp [UCT]: 2023-09-21 04:00:10 Age [y:d:h:m:s]: 01:197:03:26:33
Block: 852715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401979 RingCT/type: yes/0
Extra: 01b02e06e66fc4de6e0bd18540a5c403353b8db6c7e543ce07486b0374e8365659021100000004faf35c9c000000000000000000

1 output(s) for total of 0.917489872000 dcy

stealth address amount amount idx
00: 5f97767085e946f67176adc2e6b4f028667fe591127b4b7265b0192348d9e83d 0.917489872000 1306567 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": 852725, "vin": [ { "gen": { "height": 852715 } } ], "vout": [ { "amount": 917489872, "target": { "key": "5f97767085e946f67176adc2e6b4f028667fe591127b4b7265b0192348d9e83d" } } ], "extra": [ 1, 176, 46, 6, 230, 111, 196, 222, 110, 11, 209, 133, 64, 165, 196, 3, 53, 59, 141, 182, 199, 229, 67, 206, 7, 72, 107, 3, 116, 232, 54, 86, 89, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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