Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9d4ca11e91d6b74605cfe3fb9c96b40261386cdd75ba04ff5866e8fa50a264

Tx prefix hash: f5f6264a195b170f14fd5b323a5123824dbfff9461574a426c8099f9cb1515d0
Tx public key: 0269e7b62c8351692779675ee40dbb16c2c904f781c6d6768338c0bd7b51d16c
Timestamp: 1738449452 Timestamp [UCT]: 2025-02-01 22:37:32 Age [y:d:h:m:s]: 00:292:02:00:05
Block: 1210078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206509 RingCT/type: yes/0
Extra: 010269e7b62c8351692779675ee40dbb16c2c904f781c6d6768338c0bd7b51d16c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b9a44a0305a5473db7f7a38d415c50b7eb83baf3999ba10f6fd54620aec89a 0.600000000000 1696825 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": 1210088, "vin": [ { "gen": { "height": 1210078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b9a44a0305a5473db7f7a38d415c50b7eb83baf3999ba10f6fd54620aec89a" } } ], "extra": [ 1, 2, 105, 231, 182, 44, 131, 81, 105, 39, 121, 103, 94, 228, 13, 187, 22, 194, 201, 4, 247, 129, 198, 214, 118, 131, 56, 192, 189, 123, 81, 209, 108, 2, 17, 0, 0, 0, 3, 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