Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ebafec2787f03e2d7aff91acc6545bf97a7307f8e2d72f118c7b4e7f440b7e

Tx prefix hash: 99a7f1fec85a95b1df3a64643033a4ffa3aeeacc46c4407db0d4b9c257ff16ce
Tx public key: 451677ea1b015d7588e724680ad3f2574ef2d330ea2b2236a074bb7717f5209e
Timestamp: 1733451479 Timestamp [UCT]: 2024-12-06 02:17:59 Age [y:d:h:m:s]: 01:026:23:06:05
Block: 1168971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277726 RingCT/type: yes/0
Extra: 01451677ea1b015d7588e724680ad3f2574ef2d330ea2b2236a074bb7717f5209e0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a905032e02c583a7d9f695f46bca3c748c4ae1b3442c7f624be3172dc62d3a5 0.600000000000 1654684 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": 1168981, "vin": [ { "gen": { "height": 1168971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a905032e02c583a7d9f695f46bca3c748c4ae1b3442c7f624be3172dc62d3a5" } } ], "extra": [ 1, 69, 22, 119, 234, 27, 1, 93, 117, 136, 231, 36, 104, 10, 211, 242, 87, 78, 242, 211, 48, 234, 43, 34, 54, 160, 116, 187, 119, 23, 245, 32, 158, 2, 17, 0, 0, 0, 7, 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