Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0b3be810a5384f670f33591847724be765b8941d7762e1b3da79e3f019e7f5

Tx prefix hash: 7cff162c202e8fcb8f12bfa7ed3e3a160bfa58107158cdd461b5079990634b2b
Tx public key: ed02f5e4c83334168ac5dd99d375e6f635c9733cd9bb8fba7d230b3463d8ad52
Timestamp: 1734075958 Timestamp [UCT]: 2024-12-13 07:45:58 Age [y:d:h:m:s]: 00:102:02:05:42
Block: 1174170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72722 RingCT/type: yes/0
Extra: 01ed02f5e4c83334168ac5dd99d375e6f635c9733cd9bb8fba7d230b3463d8ad520211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22ca81bd1d498a74e3362ebd5b1ebd338c0d96d6ef76f3ea54599fa9f06d68aa 0.600000000000 1660287 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": 1174180, "vin": [ { "gen": { "height": 1174170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22ca81bd1d498a74e3362ebd5b1ebd338c0d96d6ef76f3ea54599fa9f06d68aa" } } ], "extra": [ 1, 237, 2, 245, 228, 200, 51, 52, 22, 138, 197, 221, 153, 211, 117, 230, 246, 53, 201, 115, 60, 217, 187, 143, 186, 125, 35, 11, 52, 99, 216, 173, 82, 2, 17, 0, 0, 0, 2, 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