Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa88cc080a69fe23219f6129e0b4162988f5adc2ad52686a7a8b20e01f75f1c3

Tx prefix hash: 5c8501d9a37ae353135444a750608193343b610b78f9549fea4f1501ac3b8851
Tx public key: 649c4fc7f89cb7dfb56844bc50b23ab36892a08361c94c33a5cd0467a3a3639a
Timestamp: 1712302830 Timestamp [UCT]: 2024-04-05 07:40:30 Age [y:d:h:m:s]: 00:325:04:17:01
Block: 993714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232487 RingCT/type: yes/0
Extra: 01649c4fc7f89cb7dfb56844bc50b23ab36892a08361c94c33a5cd0467a3a3639a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2715a872efe635642fc7edf7a545ff6f63476aa68e88e1a02c43d82e860d62d7 0.600000000000 1454102 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": 993724, "vin": [ { "gen": { "height": 993714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2715a872efe635642fc7edf7a545ff6f63476aa68e88e1a02c43d82e860d62d7" } } ], "extra": [ 1, 100, 156, 79, 199, 248, 156, 183, 223, 181, 104, 68, 188, 80, 178, 58, 179, 104, 146, 160, 131, 97, 201, 76, 51, 165, 205, 4, 103, 163, 163, 99, 154, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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