Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c4d4abfae60210688c094104288e9d624b9b01f052bc6ab6d697713bedc708a

Tx prefix hash: 132f8388fcfd9e3e263d1b651108b932b2f392dca31e28c0e3e7ddb5d12a347d
Tx public key: f334b9217e16b40b38c84e14c91d438395d8c7ec71357a8d96a92fde3be6e24e
Timestamp: 1707675412 Timestamp [UCT]: 2024-02-11 18:16:52 Age [y:d:h:m:s]: 01:058:11:39:57
Block: 955374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302845 RingCT/type: yes/0
Extra: 01f334b9217e16b40b38c84e14c91d438395d8c7ec71357a8d96a92fde3be6e24e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78c03bdcd0b4eceb1a618ac8256faa492710612e94f1a4324d1736e577bdef1d 0.600000000000 1414662 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": 955384, "vin": [ { "gen": { "height": 955374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78c03bdcd0b4eceb1a618ac8256faa492710612e94f1a4324d1736e577bdef1d" } } ], "extra": [ 1, 243, 52, 185, 33, 126, 22, 180, 11, 56, 200, 78, 20, 201, 29, 67, 131, 149, 216, 199, 236, 113, 53, 122, 141, 150, 169, 47, 222, 59, 230, 226, 78, 2, 17, 0, 0, 0, 5, 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