Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1c3d22a0ff463f1e276aa03512f2c05cf8a61b4305616526ba44925e841b8af

Tx prefix hash: f0b4bda2a756713566aeb820152912e34683c92472ffacfbfb7f9c071372389d
Tx public key: 2a8b74496bbc9e17713f712caf19c6fa9331a6b9daa4e4bfe41639a172b8d130
Timestamp: 1736733590 Timestamp [UCT]: 2025-01-13 01:59:50 Age [y:d:h:m:s]: 00:065:09:40:17
Block: 1196145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46531 RingCT/type: yes/0
Extra: 012a8b74496bbc9e17713f712caf19c6fa9331a6b9daa4e4bfe41639a172b8d1300211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4627b58851da29c92843ae7a718e235e47df14ed039178068630a813a007e8e5 0.600000000000 1682742 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": 1196155, "vin": [ { "gen": { "height": 1196145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4627b58851da29c92843ae7a718e235e47df14ed039178068630a813a007e8e5" } } ], "extra": [ 1, 42, 139, 116, 73, 107, 188, 158, 23, 113, 63, 113, 44, 175, 25, 198, 250, 147, 49, 166, 185, 218, 164, 228, 191, 228, 22, 57, 161, 114, 184, 209, 48, 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