Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41fdb348015a0cb4e15946dea7d7816e7acf340fe07b16191830c3237d713d8

Tx prefix hash: 412e60f1987f8e441adecf698717dde5ba21405ffd45b95de9055a87832f6977
Tx public key: 7b9df2b0ca21da576d682eeedd904f8c25f07cfb1bad347d5a3ff4d4790c3e0e
Timestamp: 1713149610 Timestamp [UCT]: 2024-04-15 02:53:30 Age [y:d:h:m:s]: 01:035:10:32:58
Block: 1000745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286323 RingCT/type: yes/0
Extra: 017b9df2b0ca21da576d682eeedd904f8c25f07cfb1bad347d5a3ff4d4790c3e0e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 007b52a095b08c3d8c29303b80745b5716d40321fb31f22b268759f02d2f3bb3 0.600000000000 1461245 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": 1000755, "vin": [ { "gen": { "height": 1000745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "007b52a095b08c3d8c29303b80745b5716d40321fb31f22b268759f02d2f3bb3" } } ], "extra": [ 1, 123, 157, 242, 176, 202, 33, 218, 87, 109, 104, 46, 238, 221, 144, 79, 140, 37, 240, 124, 251, 27, 173, 52, 125, 90, 63, 244, 212, 121, 12, 62, 14, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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