Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92e5fdea960b38ee4e26e1a3799ccf3a5bd2e41bd92b49f7b3ed4e9a5ce4c14b

Tx prefix hash: 65fb4733476dfbad0da7b155965846b2d2e34b7a35dac03a8c6c0a4404ef2170
Tx public key: 4705e899eb7d204f5a16f9f01bcc0cc98fa15e7077742854945df835d2f32ef9
Timestamp: 1718539532 Timestamp [UCT]: 2024-06-16 12:05:32 Age [y:d:h:m:s]: 00:209:07:39:37
Block: 1045462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149768 RingCT/type: yes/0
Extra: 014705e899eb7d204f5a16f9f01bcc0cc98fa15e7077742854945df835d2f32ef902110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 990b9cdb717330b215f62aed21f286679fb51e59d5e35c9c44efbed235560be1 0.600000000000 1515041 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": 1045472, "vin": [ { "gen": { "height": 1045462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "990b9cdb717330b215f62aed21f286679fb51e59d5e35c9c44efbed235560be1" } } ], "extra": [ 1, 71, 5, 232, 153, 235, 125, 32, 79, 90, 22, 249, 240, 27, 204, 12, 201, 143, 161, 94, 112, 119, 116, 40, 84, 148, 93, 248, 53, 210, 243, 46, 249, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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