Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee1bc55d6f06b8eab95f38209a71e14c18c12207c1a771a96f7c49a3ff717ab

Tx prefix hash: 1ef54295b1a0f463e5aea98980fc9af14f5342353c190bdad2c9e13999fd40aa
Tx public key: 2e2cfce7a7f96922a6d1414b71dc938b1152a8d6d6c3b36df877d499161aa987
Timestamp: 1683374160 Timestamp [UCT]: 2023-05-06 11:56:00 Age [y:d:h:m:s]: 02:157:02:56:33
Block: 754167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 632068 RingCT/type: yes/0
Extra: 012e2cfce7a7f96922a6d1414b71dc938b1152a8d6d6c3b36df877d499161aa987021100000004faf35c9c000000000000000000

1 output(s) for total of 1.945950803000 dcy

stealth address amount amount idx
00: 33a040088839534a2b65af1734da17ee90becd11a5f21fd831c35139eeb0d8b8 1.945950803000 1202420 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": 754177, "vin": [ { "gen": { "height": 754167 } } ], "vout": [ { "amount": 1945950803, "target": { "key": "33a040088839534a2b65af1734da17ee90becd11a5f21fd831c35139eeb0d8b8" } } ], "extra": [ 1, 46, 44, 252, 231, 167, 249, 105, 34, 166, 209, 65, 75, 113, 220, 147, 139, 17, 82, 168, 214, 214, 195, 179, 109, 248, 119, 212, 153, 22, 26, 169, 135, 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