Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810b1736d0594bb9d2fdf1d0cf7e03230dcf858a9559d40bb19684ed1c0a7459

Tx prefix hash: a4eea4859d7fba42010344ac2893a9a8fb9e0ef632631b3ae37d28c517353ea9
Tx public key: bb661c5e2a4a4f7f3142f83b0a85b9b687d31bc1c5b8e69b0d48ad09a89ff2f3
Timestamp: 1739153592 Timestamp [UCT]: 2025-02-10 02:13:12 Age [y:d:h:m:s]: 00:351:20:05:36
Block: 1215907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249128 RingCT/type: yes/0
Extra: 01bb661c5e2a4a4f7f3142f83b0a85b9b687d31bc1c5b8e69b0d48ad09a89ff2f30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a87ca6e5559e208bdfc9581f8ea29ac82e8770734048a5d85957ebb6c5b94a 0.600000000000 1702706 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": 1215917, "vin": [ { "gen": { "height": 1215907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a87ca6e5559e208bdfc9581f8ea29ac82e8770734048a5d85957ebb6c5b94a" } } ], "extra": [ 1, 187, 102, 28, 94, 42, 74, 79, 127, 49, 66, 248, 59, 10, 133, 185, 182, 135, 211, 27, 193, 197, 184, 230, 155, 13, 72, 173, 9, 168, 159, 242, 243, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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