Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec68091bbd8248a95c516e46beaf96f8c890b03fa6dd6bc0e3c5096126504411

Tx prefix hash: 9305b9708216b607ca397b654452b2574ab2b262feee07cf7a3f204f8ce57cb9
Tx public key: b9a0d8a1f2af9d1e57c8855a9e802883f0c515a406a3656f693896b6f9bdf1f4
Timestamp: 1699360000 Timestamp [UCT]: 2023-11-07 12:26:40 Age [y:d:h:m:s]: 01:146:03:41:29
Block: 886442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365635 RingCT/type: yes/0
Extra: 01b9a0d8a1f2af9d1e57c8855a9e802883f0c515a406a3656f693896b6f9bdf1f402110000000875e3f0e9000000000000000000

1 output(s) for total of 0.709332204000 dcy

stealth address amount amount idx
00: ceda85d18f86112cd84b11a4614f5a8e7fc9c3b52fb234f09b6fdcf01d8eef0c 0.709332204000 1342261 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": 886452, "vin": [ { "gen": { "height": 886442 } } ], "vout": [ { "amount": 709332204, "target": { "key": "ceda85d18f86112cd84b11a4614f5a8e7fc9c3b52fb234f09b6fdcf01d8eef0c" } } ], "extra": [ 1, 185, 160, 216, 161, 242, 175, 157, 30, 87, 200, 133, 90, 158, 128, 40, 131, 240, 197, 21, 164, 6, 163, 101, 111, 105, 56, 150, 182, 249, 189, 241, 244, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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