Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f266cec96403d5487cdf38688cdc5f9d8dea7b665bb08c4c651b44f7a9035c2c

Tx prefix hash: 61551a7e1b47448b245c8c22a3aa7d57a237be2af8999ede625ab57124d4ec99
Tx public key: 88adbbf1d96fb0fe011dd10ec045d78feab2ea7cf86664cd7207a8e108c01000
Timestamp: 1723396646 Timestamp [UCT]: 2024-08-11 17:17:26 Age [y:d:h:m:s]: 00:237:20:13:03
Block: 1085717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169853 RingCT/type: yes/0
Extra: 0188adbbf1d96fb0fe011dd10ec045d78feab2ea7cf86664cd7207a8e108c01000021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38779cf5f418709b16ae2b38dd69d1373c5aefb60b2b422ca88f37ddc5e6db3 0.600000000000 1560306 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": 1085727, "vin": [ { "gen": { "height": 1085717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38779cf5f418709b16ae2b38dd69d1373c5aefb60b2b422ca88f37ddc5e6db3" } } ], "extra": [ 1, 136, 173, 187, 241, 217, 111, 176, 254, 1, 29, 209, 14, 192, 69, 215, 143, 234, 178, 234, 124, 248, 102, 100, 205, 114, 7, 168, 225, 8, 192, 16, 0, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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