Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df1e7b1903de59680e5c77e1f29dd637dd6f6ea4a470993ebd2d91f4d986a60e

Tx prefix hash: a13a0cfe0f0c3a67ed6dc06f185ae0d89fba34589cd3655546e271a9602fdec7
Tx public key: d6093a2310e04b92099865e0099d54adfaa3ea6e35f2cdcba63efc2b22c84f3e
Timestamp: 1638798833 Timestamp [UCT]: 2021-12-06 13:53:53 Age [y:d:h:m:s]: 02:361:00:16:10
Block: 389698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776044 RingCT/type: yes/0
Extra: 01d6093a2310e04b92099865e0099d54adfaa3ea6e35f2cdcba63efc2b22c84f3e021100000001d6e4826b000000000000000000

1 output(s) for total of 31.388395862000 dcy

stealth address amount amount idx
00: 10d99d8ca807961a8ebca64dc9a0046efc70cb7f54a76a3584d683c0a8ef71e9 31.388395862000 785007 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": 389708, "vin": [ { "gen": { "height": 389698 } } ], "vout": [ { "amount": 31388395862, "target": { "key": "10d99d8ca807961a8ebca64dc9a0046efc70cb7f54a76a3584d683c0a8ef71e9" } } ], "extra": [ 1, 214, 9, 58, 35, 16, 224, 75, 146, 9, 152, 101, 224, 9, 157, 84, 173, 250, 163, 234, 110, 53, 242, 205, 203, 166, 62, 252, 43, 34, 200, 79, 62, 2, 17, 0, 0, 0, 1, 214, 228, 130, 107, 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