Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf8247abf8044f4380eea0f1424d6459b1118505d108ce42acf777d181f7227

Tx prefix hash: 6461ff4eaa351714f4efc92570b81284cecdf52a1906eaddf8200f3703cd84c8
Tx public key: 72a21bb3ccee241055539d0b07e0aeded536df46423e46dfba41d9b66a9f8af5
Timestamp: 1698288773 Timestamp [UCT]: 2023-10-26 02:52:53 Age [y:d:h:m:s]: 01:166:19:43:51
Block: 877770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380228 RingCT/type: yes/0
Extra: 0172a21bb3ccee241055539d0b07e0aeded536df46423e46dfba41d9b66a9f8af50211000000064b8f5122000000000000000000

1 output(s) for total of 0.757850648000 dcy

stealth address amount amount idx
00: ad8a438949a8f4209d8b8da2b7144f976613bdc73ae9d066a8d3f77658aeb86b 0.757850648000 1333158 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": 877780, "vin": [ { "gen": { "height": 877770 } } ], "vout": [ { "amount": 757850648, "target": { "key": "ad8a438949a8f4209d8b8da2b7144f976613bdc73ae9d066a8d3f77658aeb86b" } } ], "extra": [ 1, 114, 162, 27, 179, 204, 238, 36, 16, 85, 83, 157, 11, 7, 224, 174, 222, 213, 54, 223, 70, 66, 62, 70, 223, 186, 65, 217, 182, 106, 159, 138, 245, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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