Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e54a2af7a4ad07b9ec585140dc24f469e040757f02fc5db9c9bd48d67b91ee3

Tx prefix hash: c6f325778aab0fcf94522a1f1c0e502464e5b787d6d70d348c5623d378681941
Tx public key: c2b948cf6d8e0ed09aceeec6a3f815df61aae82ad696854a493205f7bb8119a2
Timestamp: 1576472198 Timestamp [UCT]: 2019-12-16 04:56:38 Age [y:d:h:m:s]: 05:019:17:12:29
Block: 27894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160984 RingCT/type: yes/0
Extra: 01c2b948cf6d8e0ed09aceeec6a3f815df61aae82ad696854a493205f7bb8119a202110000006dad433a0b000000000000000000

1 output(s) for total of 496.116826966000 dcy

stealth address amount amount idx
00: a0b2ed1190b8479897ce8301f50fa07eefb6b9ff6a38788d4f4e3244f3f1d7a3 496.116826966000 46078 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": 27904, "vin": [ { "gen": { "height": 27894 } } ], "vout": [ { "amount": 496116826966, "target": { "key": "a0b2ed1190b8479897ce8301f50fa07eefb6b9ff6a38788d4f4e3244f3f1d7a3" } } ], "extra": [ 1, 194, 185, 72, 207, 109, 142, 14, 208, 154, 206, 238, 198, 163, 248, 21, 223, 97, 170, 232, 42, 214, 150, 133, 74, 73, 50, 5, 247, 187, 129, 25, 162, 2, 17, 0, 0, 0, 109, 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