Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbda048a241bc6ffb97129ed166982474b45d3ec8be2bb47fc35fea0c9ddde12

Tx prefix hash: b29ce8f965b920e7785a05ef42521b8dc26faa5175d6dbdcb512bbe3238a3599
Tx public key: b179d5b2e226d7e0c06f1e0e6e06f94cb096dd59f9f2cb0aab091065e577a9b6
Timestamp: 1697114160 Timestamp [UCT]: 2023-10-12 12:36:00 Age [y:d:h:m:s]: 01:186:07:21:50
Block: 868043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394175 RingCT/type: yes/0
Extra: 01b179d5b2e226d7e0c06f1e0e6e06f94cb096dd59f9f2cb0aab091065e577a9b602110000000f75e3f0e9000000000000000000

1 output(s) for total of 0.816231271000 dcy

stealth address amount amount idx
00: b8359f3fde1de481da686f1ad1a8c055f138eb04333a7e413ef954f3b80c606d 0.816231271000 1322796 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": 868053, "vin": [ { "gen": { "height": 868043 } } ], "vout": [ { "amount": 816231271, "target": { "key": "b8359f3fde1de481da686f1ad1a8c055f138eb04333a7e413ef954f3b80c606d" } } ], "extra": [ 1, 177, 121, 213, 178, 226, 38, 215, 224, 192, 111, 30, 14, 110, 6, 249, 76, 176, 150, 221, 89, 249, 242, 203, 10, 171, 9, 16, 101, 229, 119, 169, 182, 2, 17, 0, 0, 0, 15, 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