Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e0bf8093c8154c1407cde112a29d10e8299d882b13ab7fa6a40328d581b0bf

Tx prefix hash: 89b5e2d6cbe1a3cdf5f98b90bca1dab728f1d626942d44346c8460ad22223f5d
Tx public key: fbee2393e332d6b1aab7113e1d354f65dd0ad94897150ad8007b7ff8dd437d8a
Timestamp: 1759151003 Timestamp [UCT]: 2025-09-29 13:03:23 Age [y:d:h:m:s]: 00:008:21:10:37
Block: 1379020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6346 RingCT/type: yes/0
Extra: 01fbee2393e332d6b1aab7113e1d354f65dd0ad94897150ad8007b7ff8dd437d8a021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c9e5a3d98bacc7aaf8af64b0d074ff24a479ab3a573368cc0341b939c40a55e 0.600000000000 1867117 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": 1379030, "vin": [ { "gen": { "height": 1379020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c9e5a3d98bacc7aaf8af64b0d074ff24a479ab3a573368cc0341b939c40a55e" } } ], "extra": [ 1, 251, 238, 35, 147, 227, 50, 214, 177, 170, 183, 17, 62, 29, 53, 79, 101, 221, 10, 217, 72, 151, 21, 10, 216, 0, 123, 127, 248, 221, 67, 125, 138, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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