Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd38b1e4bd1947a396960eac6059c9150548f5fb0af6739dfdc1cd68ed332ad2

Tx prefix hash: d8327b3e3d03dd95e95ec72045b351a0b4eaacda527da5f813ee41c20ffe1d7d
Tx public key: cc7555e3bf6d162c30acdbcdd7e0b556f3d50fc4296712eafa3aa9b3de26e564
Timestamp: 1737356411 Timestamp [UCT]: 2025-01-20 07:00:11 Age [y:d:h:m:s]: 00:331:01:48:55
Block: 1201248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234208 RingCT/type: yes/0
Extra: 01cc7555e3bf6d162c30acdbcdd7e0b556f3d50fc4296712eafa3aa9b3de26e564021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ac2c6a98e2a224b18e58d4db5a6f555533d31f49a933984b3895288bf71b90 0.600000000000 1687897 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": 1201258, "vin": [ { "gen": { "height": 1201248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ac2c6a98e2a224b18e58d4db5a6f555533d31f49a933984b3895288bf71b90" } } ], "extra": [ 1, 204, 117, 85, 227, 191, 109, 22, 44, 48, 172, 219, 205, 215, 224, 181, 86, 243, 213, 15, 196, 41, 103, 18, 234, 250, 58, 169, 179, 222, 38, 229, 100, 2, 17, 0, 0, 0, 2, 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