Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dc249fbf1aa93d4c4387da0ceebede2cbb8d141bdf936e2c1de62335f1eaeac

Tx prefix hash: 76ee1411ab5c6b28f49fd94ffd6089e60c6c758e5300d97505cb0f42618f5ec1
Tx public key: 01e0d98f414ee4222368a0381d83a4d524fa4ccf3f9c8d0be77e91193046d0c9
Timestamp: 1701482259 Timestamp [UCT]: 2023-12-02 01:57:39 Age [y:d:h:m:s]: 01:084:06:12:16
Block: 904018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321344 RingCT/type: yes/0
Extra: 0101e0d98f414ee4222368a0381d83a4d524fa4ccf3f9c8d0be77e91193046d0c902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.620316121000 dcy

stealth address amount amount idx
00: faf85f657260d3b9b01a4245648122f81c43fc83e3c73540e90cf0f92015be9a 0.620316121000 1360721 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": 904028, "vin": [ { "gen": { "height": 904018 } } ], "vout": [ { "amount": 620316121, "target": { "key": "faf85f657260d3b9b01a4245648122f81c43fc83e3c73540e90cf0f92015be9a" } } ], "extra": [ 1, 1, 224, 217, 143, 65, 78, 228, 34, 35, 104, 160, 56, 29, 131, 164, 213, 36, 250, 76, 207, 63, 156, 141, 11, 231, 126, 145, 25, 48, 70, 208, 201, 2, 17, 0, 0, 0, 4, 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