Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c964400ff1c987cdb9499e48ead7df8cc5719d7063f6b7366ea57159d331263

Tx prefix hash: 252ffbf70176248d67aeffecf9fa932bef0673c23d23a008dcedaa55a00837c7
Tx public key: 316065e9a6f789f99118e5f3b431cb6cc5e06f34935aaff58caf527c7e2b1c6a
Timestamp: 1710522370 Timestamp [UCT]: 2024-03-15 17:06:10 Age [y:d:h:m:s]: 01:062:12:12:19
Block: 979001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305664 RingCT/type: yes/0
Extra: 01316065e9a6f789f99118e5f3b431cb6cc5e06f34935aaff58caf527c7e2b1c6a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f226dc4e4ab01c7b7a9ec373853f861d052d562c27965b8ebe0e45e8827633fa 0.600000000000 1439030 of 15

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": 979011, "vin": [ { "gen": { "height": 979001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f226dc4e4ab01c7b7a9ec373853f861d052d562c27965b8ebe0e45e8827633fa" } } ], "extra": [ 1, 49, 96, 101, 233, 166, 247, 137, 249, 145, 24, 229, 243, 180, 49, 203, 108, 197, 224, 111, 52, 147, 90, 175, 245, 140, 175, 82, 124, 126, 43, 28, 106, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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