Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b71bd5e7495336ab6d35d33c16424c7c5d9d3ee8227257681e523bdef2b671

Tx prefix hash: 0ab74215e9e94255190436ebff854f0428124cabcaa67652f1b7b4e843211da0
Tx public key: b58ebc0870191aa96768b2a2e7efe9745b57827df26c1e384fe7c0fe95e8225a
Timestamp: 1711310424 Timestamp [UCT]: 2024-03-24 20:00:24 Age [y:d:h:m:s]: 01:051:03:00:58
Block: 985532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297527 RingCT/type: yes/0
Extra: 01b58ebc0870191aa96768b2a2e7efe9745b57827df26c1e384fe7c0fe95e8225a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f1df4991d744b720c201d17a219b5f6fb1c6b7b1b6fb1e5517ca51598e6eb0a 0.600000000000 1445745 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": 985542, "vin": [ { "gen": { "height": 985532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f1df4991d744b720c201d17a219b5f6fb1c6b7b1b6fb1e5517ca51598e6eb0a" } } ], "extra": [ 1, 181, 142, 188, 8, 112, 25, 26, 169, 103, 104, 178, 162, 231, 239, 233, 116, 91, 87, 130, 125, 242, 108, 30, 56, 79, 231, 192, 254, 149, 232, 34, 90, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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