Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890272816299bf997e57d6015b164f4efe281e5cb6274167cf7560e36a35aa4c

Tx prefix hash: 45e1606c42d31fd8311b8c8fd68c042ee64059c61dbf3a47839e67acdf1fb0ec
Tx public key: 2a03d1e0a39cccbd739e758c9c485430d12b29067014a04f2a1bb127f55d3b52
Timestamp: 1730085763 Timestamp [UCT]: 2024-10-28 03:22:43 Age [y:d:h:m:s]: 01:011:09:08:03
Block: 1141104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266536 RingCT/type: yes/0
Extra: 012a03d1e0a39cccbd739e758c9c485430d12b29067014a04f2a1bb127f55d3b5202110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93d8312d15753ead17b9923049c513270fc7784bff40b036dd748cf1103d46a6 0.600000000000 1624911 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": 1141114, "vin": [ { "gen": { "height": 1141104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93d8312d15753ead17b9923049c513270fc7784bff40b036dd748cf1103d46a6" } } ], "extra": [ 1, 42, 3, 209, 224, 163, 156, 204, 189, 115, 158, 117, 140, 156, 72, 84, 48, 209, 43, 41, 6, 112, 20, 160, 79, 42, 27, 177, 39, 245, 93, 59, 82, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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