Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735def739670f359e0bc21cccd3d6caecc264eda42f6f27a50b34f76ab65b7d9

Tx prefix hash: cc3cff39cd5fbea43d7e2ad6a21c7cb33e0a86f1530bc72616156a65371c63ce
Tx public key: b60c9a8f934b4d4f100f7b8091160374336ef7daec46e1bb006a9c59ad695ce2
Timestamp: 1721967288 Timestamp [UCT]: 2024-07-26 04:14:48 Age [y:d:h:m:s]: 00:321:09:37:53
Block: 1073859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229626 RingCT/type: yes/0
Extra: 01b60c9a8f934b4d4f100f7b8091160374336ef7daec46e1bb006a9c59ad695ce2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f20121c123462f83835dd6443c8a6b726054b5c95ebcab3f7fb17065cb70b14 0.600000000000 1546366 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": 1073869, "vin": [ { "gen": { "height": 1073859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f20121c123462f83835dd6443c8a6b726054b5c95ebcab3f7fb17065cb70b14" } } ], "extra": [ 1, 182, 12, 154, 143, 147, 75, 77, 79, 16, 15, 123, 128, 145, 22, 3, 116, 51, 110, 247, 218, 236, 70, 225, 187, 0, 106, 156, 89, 173, 105, 92, 226, 2, 17, 0, 0, 0, 5, 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