Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454fc46c9f1a2f382bf4d315172c4bc5401f732c6b00559d7473457ca03ec982

Tx prefix hash: e40ab856b356855ed5783aa48b48f8895fd7195437a5647e6f661d78a1428d12
Tx public key: 157f98050aed4cb873b312b5242e2273f4c8f3ea9f0c493318906adb298fd72a
Timestamp: 1725779722 Timestamp [UCT]: 2024-09-08 07:15:22 Age [y:d:h:m:s]: 00:233:05:39:33
Block: 1105471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166560 RingCT/type: yes/0
Extra: 01157f98050aed4cb873b312b5242e2273f4c8f3ea9f0c493318906adb298fd72a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66e17b62b1c4c3b1c355c4cf1c297534230f319bb91d74568f921a285eec9758 0.600000000000 1582814 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": 1105481, "vin": [ { "gen": { "height": 1105471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e17b62b1c4c3b1c355c4cf1c297534230f319bb91d74568f921a285eec9758" } } ], "extra": [ 1, 21, 127, 152, 5, 10, 237, 76, 184, 115, 179, 18, 181, 36, 46, 34, 115, 244, 200, 243, 234, 159, 12, 73, 51, 24, 144, 106, 219, 41, 143, 215, 42, 2, 17, 0, 0, 0, 4, 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