Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d432d25bc85905206bf23d25a6dcbcc33e4873b58b82b2a5a598bac399a77e

Tx prefix hash: 1bf4233adc2434d1a8a5db266e5136f4cb2ad74913244e8d285091d026c29549
Tx public key: 75bcf1eb90c944331e39e2d1acbdb848e67bdf4f380bff5777e9fdc97d0eec1e
Timestamp: 1714115149 Timestamp [UCT]: 2024-04-26 07:05:49 Age [y:d:h:m:s]: 00:258:05:58:29
Block: 1008766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184849 RingCT/type: yes/0
Extra: 0175bcf1eb90c944331e39e2d1acbdb848e67bdf4f380bff5777e9fdc97d0eec1e02110000000118ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f07ef10918cea726f3374b32ec0654d3d68e0a08ca4efab61e76628d648fcf4 0.600000000000 1470244 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": 1008776, "vin": [ { "gen": { "height": 1008766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f07ef10918cea726f3374b32ec0654d3d68e0a08ca4efab61e76628d648fcf4" } } ], "extra": [ 1, 117, 188, 241, 235, 144, 201, 68, 51, 30, 57, 226, 209, 172, 189, 184, 72, 230, 123, 223, 79, 56, 11, 255, 87, 119, 233, 253, 201, 125, 14, 236, 30, 2, 17, 0, 0, 0, 1, 24, 236, 144, 96, 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