Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed0462369e8ada66b2830e66d2705ae8b1347ca9b8d39306617e3f574415c368

Tx prefix hash: 70ef1d27e72a50d5421dd135ba1ab756ef1b66b60bfc364e3d3609fffd2162ef
Tx public key: 854c144a8f6ba7aca71e6fbb937742ae3aeef40b9411f091c7b815a58b05ccf1
Timestamp: 1728590292 Timestamp [UCT]: 2024-10-10 19:58:12 Age [y:d:h:m:s]: 00:103:15:55:02
Block: 1128776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74055 RingCT/type: yes/0
Extra: 01854c144a8f6ba7aca71e6fbb937742ae3aeef40b9411f091c7b815a58b05ccf102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b82e5770fd4a698546908d905e01fcf564532ffa2be6790d6c629d1d4ef89441 0.600000000000 1611597 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": 1128786, "vin": [ { "gen": { "height": 1128776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b82e5770fd4a698546908d905e01fcf564532ffa2be6790d6c629d1d4ef89441" } } ], "extra": [ 1, 133, 76, 20, 74, 143, 107, 167, 172, 167, 30, 111, 187, 147, 119, 66, 174, 58, 238, 244, 11, 148, 17, 240, 145, 199, 184, 21, 165, 139, 5, 204, 241, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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