Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 727e07e79b9ab887f58ac3d1cfac0604dfb4d0abc69f7095347ee019d6ff41f2

Tx prefix hash: d269ad8d9761c1154686741a66684e4ed7c2b0ba7de465f2e75abff5ea550485
Tx public key: 58664055daf8d8e93e05d860cc78a6de8eab8438f9ca669e3e2b7aa5d2d4b7e9
Timestamp: 1701199061 Timestamp [UCT]: 2023-11-28 19:17:41 Age [y:d:h:m:s]: 01:167:04:25:54
Block: 901689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380669 RingCT/type: yes/0
Extra: 0158664055daf8d8e93e05d860cc78a6de8eab8438f9ca669e3e2b7aa5d2d4b7e90211000000034b8f5122000000000000000000

1 output(s) for total of 0.631436983000 dcy

stealth address amount amount idx
00: 33871b5a909ebbb47ed4dd604f080dca5dc87d1cf96ca6480c7e4398529664d5 0.631436983000 1358272 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": 901699, "vin": [ { "gen": { "height": 901689 } } ], "vout": [ { "amount": 631436983, "target": { "key": "33871b5a909ebbb47ed4dd604f080dca5dc87d1cf96ca6480c7e4398529664d5" } } ], "extra": [ 1, 88, 102, 64, 85, 218, 248, 216, 233, 62, 5, 216, 96, 204, 120, 166, 222, 142, 171, 132, 56, 249, 202, 102, 158, 62, 43, 122, 165, 210, 212, 183, 233, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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