Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f7ac3db62df65291e08c4a17a459ff0f53ebd09f853f5c238ceb9c37f10d52

Tx prefix hash: db17a2a2131fc63283f66e6c1bac28d1cc2e632a985265d443370f989cd743b4
Tx public key: 8f21f26eae367e39a8b213dbca61be766ddfc6150662e8fd88c217e7a8d9c645
Timestamp: 1750024579 Timestamp [UCT]: 2025-06-15 21:56:19 Age [y:d:h:m:s]: 00:157:06:52:51
Block: 1305808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110204 RingCT/type: yes/0
Extra: 018f21f26eae367e39a8b213dbca61be766ddfc6150662e8fd88c217e7a8d9c64502110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 001f9288f0845fcc4c7216093954a2536bd34ddb84c4c0ff56de3a9c74fcdd80 0.600000000000 1793409 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": 1305818, "vin": [ { "gen": { "height": 1305808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001f9288f0845fcc4c7216093954a2536bd34ddb84c4c0ff56de3a9c74fcdd80" } } ], "extra": [ 1, 143, 33, 242, 110, 174, 54, 126, 57, 168, 178, 19, 219, 202, 97, 190, 118, 109, 223, 198, 21, 6, 98, 232, 253, 136, 194, 23, 231, 168, 217, 198, 69, 2, 17, 0, 0, 0, 1, 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