Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d064ff62e914a0adf44f72664a0f1db6dcef5d34f8309a7556074cf7e7bffec

Tx prefix hash: 4c9aeee3d621b20c6ff9ca013e8788351a044d39435746671c812831f28a107d
Tx public key: 1d229845066f6ee047a00f387dd326abed027b8d0cfe879d812f17b6134ee894
Timestamp: 1707599582 Timestamp [UCT]: 2024-02-10 21:13:02 Age [y:d:h:m:s]: 01:269:04:37:51
Block: 954742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451139 RingCT/type: yes/0
Extra: 011d229845066f6ee047a00f387dd326abed027b8d0cfe879d812f17b6134ee8940211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a6d1cd1c0df4fe47379c0952a6c895a2ba49bc772d484af31510df8fd4c727 0.600000000000 1414024 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": 954752, "vin": [ { "gen": { "height": 954742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a6d1cd1c0df4fe47379c0952a6c895a2ba49bc772d484af31510df8fd4c727" } } ], "extra": [ 1, 29, 34, 152, 69, 6, 111, 110, 224, 71, 160, 15, 56, 125, 211, 38, 171, 237, 2, 123, 141, 12, 254, 135, 157, 129, 47, 23, 182, 19, 78, 232, 148, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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