Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f965d6b266ee3c15187229a0d6695708f13a298b8b59c35356b47d8d6b4320c1

Tx prefix hash: 1e5d01066851404790f6c840f70e5ac4cb9d3249181c2fd84243c96f7b7a98aa
Tx public key: b475367d3d804cd1517b7a92a1d4cc0f5fc9d2afe11fc7c491a8ce105a4e50f8
Timestamp: 1724613159 Timestamp [UCT]: 2024-08-25 19:12:39 Age [y:d:h:m:s]: 00:251:10:34:12
Block: 1095813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179563 RingCT/type: yes/0
Extra: 01b475367d3d804cd1517b7a92a1d4cc0f5fc9d2afe11fc7c491a8ce105a4e50f802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8979688300343fd67a4e3f99eb1c5a56b3ac698871c7f76ed60e6be4bbd455b2 0.600000000000 1570996 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": 1095823, "vin": [ { "gen": { "height": 1095813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8979688300343fd67a4e3f99eb1c5a56b3ac698871c7f76ed60e6be4bbd455b2" } } ], "extra": [ 1, 180, 117, 54, 125, 61, 128, 76, 209, 81, 123, 122, 146, 161, 212, 204, 15, 95, 201, 210, 175, 225, 31, 199, 196, 145, 168, 206, 16, 90, 78, 80, 248, 2, 17, 0, 0, 0, 3, 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