Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df34aedffd3c3f5e72ee84198a2ee13903501cc1012b90c689221830796983be

Tx prefix hash: 77f159e291ff812eb010bcbfaf0fbf574b1209c64a1e7712a313361495c3daa2
Tx public key: 523906c9d1ff5c0f43874724b0309cb4484fb2a4ac8b1b52cbc373b2822e65bc
Timestamp: 1721933779 Timestamp [UCT]: 2024-07-25 18:56:19 Age [y:d:h:m:s]: 00:328:11:19:56
Block: 1073584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234570 RingCT/type: yes/0
Extra: 01523906c9d1ff5c0f43874724b0309cb4484fb2a4ac8b1b52cbc373b2822e65bc021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82dc13a39e237abff00af8ee705736431f8b939f3f014019dc0ac24a1d2a72c5 0.600000000000 1546089 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": 1073594, "vin": [ { "gen": { "height": 1073584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82dc13a39e237abff00af8ee705736431f8b939f3f014019dc0ac24a1d2a72c5" } } ], "extra": [ 1, 82, 57, 6, 201, 209, 255, 92, 15, 67, 135, 71, 36, 176, 48, 156, 180, 72, 79, 178, 164, 172, 139, 27, 82, 203, 195, 115, 178, 130, 46, 101, 188, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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