Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc5e7cb0f88b6bbd8badb242f2c1a4b3645fe458c00edb9768625ef30fab621

Tx prefix hash: 22939dc294210aed9ec93e59fcb1aed3d6a57a2d667811c8da64c3561ed54993
Tx public key: fcb04d02e8e970af14781fdec1324241f5d29497496a1d9b6c7b9c69e1ba4bca
Timestamp: 1609224938 Timestamp [UCT]: 2020-12-29 06:55:38 Age [y:d:h:m:s]: 04:039:06:01:43
Block: 171254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1041401 RingCT/type: yes/0
Extra: 01fcb04d02e8e970af14781fdec1324241f5d29497496a1d9b6c7b9c69e1ba4bca02110000034090ce5c0f000000000000000000

1 output(s) for total of 166.174764140000 dcy

stealth address amount amount idx
00: 7f0a1603fd58d277bd188def1112848117d25c76bc79f5c20b0cb7f26c5d6b60 166.174764140000 322201 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": 171264, "vin": [ { "gen": { "height": 171254 } } ], "vout": [ { "amount": 166174764140, "target": { "key": "7f0a1603fd58d277bd188def1112848117d25c76bc79f5c20b0cb7f26c5d6b60" } } ], "extra": [ 1, 252, 176, 77, 2, 232, 233, 112, 175, 20, 120, 31, 222, 193, 50, 66, 65, 245, 210, 148, 151, 73, 106, 29, 155, 108, 123, 156, 105, 225, 186, 75, 202, 2, 17, 0, 0, 3, 64, 144, 206, 92, 15, 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