Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce53a0c9a454056a2eab0b04e05e1f35a38b2201031c1e1f6fb67686305a6cd1

Tx prefix hash: 3c1c8c82182962702a51b1218c374bc842b989a734bf4b44821ab6938c101cf8
Tx public key: ae3bb5aad343e9e756f9f72393f2946a6881a9bd2ef234fae4f44a4f49e8ca4d
Timestamp: 1576644114 Timestamp [UCT]: 2019-12-18 04:41:54 Age [y:d:h:m:s]: 04:335:14:13:26
Block: 28522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126617 RingCT/type: yes/0
Extra: 01ae3bb5aad343e9e756f9f72393f2946a6881a9bd2ef234fae4f44a4f49e8ca4d021100000010ad433a0b000000000000000000

1 output(s) for total of 493.736959652000 dcy

stealth address amount amount idx
00: 64a405e20cd7aaea96aa16dd4b4f891fddd9610f0acd0dcdb085d8e0cb8396ef 493.736959652000 47072 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": 28532, "vin": [ { "gen": { "height": 28522 } } ], "vout": [ { "amount": 493736959652, "target": { "key": "64a405e20cd7aaea96aa16dd4b4f891fddd9610f0acd0dcdb085d8e0cb8396ef" } } ], "extra": [ 1, 174, 59, 181, 170, 211, 67, 233, 231, 86, 249, 247, 35, 147, 242, 148, 106, 104, 129, 169, 189, 46, 242, 52, 250, 228, 244, 74, 79, 73, 232, 202, 77, 2, 17, 0, 0, 0, 16, 173, 67, 58, 11, 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