Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c4f806fac1504024e8fe346b44691402e4dd3cc446e7c4b96a095c394fa2c8

Tx prefix hash: 661a415a8d6ec4b92034122284138f56d2cd860f01c36697d27d52a326d34603
Tx public key: dc92f6e1579313f7c5b7522c4288e4b1bbb0a0c588c1fa727431368bc488d978
Timestamp: 1715076307 Timestamp [UCT]: 2024-05-07 10:05:07 Age [y:d:h:m:s]: 00:293:19:43:41
Block: 1016739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209989 RingCT/type: yes/0
Extra: 01dc92f6e1579313f7c5b7522c4288e4b1bbb0a0c588c1fa727431368bc488d97802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d63b6c547b557e7b3bff3d91da731f11052b4bc80dd6e090614d755be685b64 0.600000000000 1480408 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": 1016749, "vin": [ { "gen": { "height": 1016739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d63b6c547b557e7b3bff3d91da731f11052b4bc80dd6e090614d755be685b64" } } ], "extra": [ 1, 220, 146, 246, 225, 87, 147, 19, 247, 197, 183, 82, 44, 66, 136, 228, 177, 187, 176, 160, 197, 136, 193, 250, 114, 116, 49, 54, 139, 196, 136, 217, 120, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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