Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b7cf5ab0ad3d2d1f48a31443c9bed21396ac4adca3a0e5948151d13c6efdf84

Tx prefix hash: 33a81961ed67e455f164b29626a32e0d8a929b055df03a53b5c815017896f5b9
Tx public key: b1d42973b534dd4d2794ecd6cce6305ececae4cc96177fc08c7fcdac97545a31
Timestamp: 1724774812 Timestamp [UCT]: 2024-08-27 16:06:52 Age [y:d:h:m:s]: 00:293:12:26:29
Block: 1097132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209575 RingCT/type: yes/0
Extra: 01b1d42973b534dd4d2794ecd6cce6305ececae4cc96177fc08c7fcdac97545a31021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10cb1a89fb8033f35f76702c37c975be258de4c86be9fc9df804e2258e5af85 0.600000000000 1572443 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": 1097142, "vin": [ { "gen": { "height": 1097132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10cb1a89fb8033f35f76702c37c975be258de4c86be9fc9df804e2258e5af85" } } ], "extra": [ 1, 177, 212, 41, 115, 181, 52, 221, 77, 39, 148, 236, 214, 204, 230, 48, 94, 206, 202, 228, 204, 150, 23, 127, 192, 140, 127, 205, 172, 151, 84, 90, 49, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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