Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f95029114b55a419acc0bbf745827da81cc8aefea9c5eb8c22166f6d9533970

Tx prefix hash: 07545099d9988359aa22d97ec477ddfbfc87dabc49b3100d9abcf89d13d860e6
Tx public key: da14a0a17bf3c7845747dcc7142416fa4de27d5b6a7de8794b57b1ea52bc3dab
Timestamp: 1725950576 Timestamp [UCT]: 2024-09-10 06:42:56 Age [y:d:h:m:s]: 00:230:13:26:01
Block: 1106886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164643 RingCT/type: yes/0
Extra: 01da14a0a17bf3c7845747dcc7142416fa4de27d5b6a7de8794b57b1ea52bc3dab021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e4a14e0916ed1e3e7a17f43cd3b060614d611c6ab85e285c8d5a93243609ba6 0.600000000000 1584489 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": 1106896, "vin": [ { "gen": { "height": 1106886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e4a14e0916ed1e3e7a17f43cd3b060614d611c6ab85e285c8d5a93243609ba6" } } ], "extra": [ 1, 218, 20, 160, 161, 123, 243, 199, 132, 87, 71, 220, 199, 20, 36, 22, 250, 77, 226, 125, 91, 106, 125, 232, 121, 75, 87, 177, 234, 82, 188, 61, 171, 2, 17, 0, 0, 0, 6, 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