Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eef0ddb0c5a1d92bae62563c8f3a17f20e78d76556a1ac28c81c83ff430a458

Tx prefix hash: ddcc57a527349f1035c662d530c0746ee3667151817d1a6497a956c36266bc3b
Tx public key: 73f1601852798cb4db8e971fc70bf6f50b8942fab853cf820e966b467c2847da
Timestamp: 1726586909 Timestamp [UCT]: 2024-09-17 15:28:29 Age [y:d:h:m:s]: 01:051:15:00:35
Block: 1112159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295308 RingCT/type: yes/0
Extra: 0173f1601852798cb4db8e971fc70bf6f50b8942fab853cf820e966b467c2847da02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ffd7fcceddf281652da6d7a2fed13e2b1d2b4338cba83c608e71e976a5ccf4f 0.600000000000 1591380 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": 1112169, "vin": [ { "gen": { "height": 1112159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ffd7fcceddf281652da6d7a2fed13e2b1d2b4338cba83c608e71e976a5ccf4f" } } ], "extra": [ 1, 115, 241, 96, 24, 82, 121, 140, 180, 219, 142, 151, 31, 199, 11, 246, 245, 11, 137, 66, 250, 184, 83, 207, 130, 14, 150, 107, 70, 124, 40, 71, 218, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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