Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 032ea15b82442e49d13965a13c077b1df4b088b4c9cfd7920fb16a29cfc37949

Tx prefix hash: cfb4f7fae442e68ac649fb43b8137aac924e642c7f2f71d560d94de1923cf41c
Tx public key: 1c6e9cce439e4a57bc52cd517c00d844e7fdc964746744bda9bef61942940a61
Timestamp: 1730673778 Timestamp [UCT]: 2024-11-03 22:42:58 Age [y:d:h:m:s]: 00:136:17:26:44
Block: 1145960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97567 RingCT/type: yes/0
Extra: 011c6e9cce439e4a57bc52cd517c00d844e7fdc964746744bda9bef61942940a610211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 585900d0ef67d5552ba2f1d95ca1453f66278e84eb3b444d1a2c8564165756c4 0.600000000000 1630495 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": 1145970, "vin": [ { "gen": { "height": 1145960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "585900d0ef67d5552ba2f1d95ca1453f66278e84eb3b444d1a2c8564165756c4" } } ], "extra": [ 1, 28, 110, 156, 206, 67, 158, 74, 87, 188, 82, 205, 81, 124, 0, 216, 68, 231, 253, 201, 100, 116, 103, 68, 189, 169, 190, 246, 25, 66, 148, 10, 97, 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