Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87fb9bad394e5b0ffc80e4b41b0bc0e7483ece553879735a5d882b6779e4aa8

Tx prefix hash: dc57fd591fa875cd4a6bb7f7ddd8d5b6bc4a177d5bee63efcd96acc6a334108e
Tx public key: 7e7d85ef5b80310c77c996f394542fa3e342556fde6c6f11be333292b4b0303d
Timestamp: 1738495291 Timestamp [UCT]: 2025-02-02 11:21:31 Age [y:d:h:m:s]: 00:335:09:15:38
Block: 1210452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237549 RingCT/type: yes/0
Extra: 017e7d85ef5b80310c77c996f394542fa3e342556fde6c6f11be333292b4b0303d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9621a366fa24d89241f64e0fe1f676647223697dd1f8cfa11706f3a86dea2f5 0.600000000000 1697205 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": 1210462, "vin": [ { "gen": { "height": 1210452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9621a366fa24d89241f64e0fe1f676647223697dd1f8cfa11706f3a86dea2f5" } } ], "extra": [ 1, 126, 125, 133, 239, 91, 128, 49, 12, 119, 201, 150, 243, 148, 84, 47, 163, 227, 66, 85, 111, 222, 108, 111, 17, 190, 51, 50, 146, 180, 176, 48, 61, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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