Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f819708ca323a02be5c258860c0074b05286a554648397445f2c06b016e6e7d

Tx prefix hash: 74f5ae829fe52812a266524f29856ccda9f129f6e308a5e3de6e4d672054657b
Tx public key: 067d7a48811341e56733e2988f2a46586d475e4a77ba709d4494b85d668ae4a0
Timestamp: 1749492635 Timestamp [UCT]: 2025-06-09 18:10:35 Age [y:d:h:m:s]: 00:154:19:19:11
Block: 1301521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108305 RingCT/type: yes/0
Extra: 01067d7a48811341e56733e2988f2a46586d475e4a77ba709d4494b85d668ae4a0021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4c02cb5326c0efda4fd43eb4c6929a0c2800ddab66ef63b60f19bd22f3c18a 0.600000000000 1789080 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": 1301531, "vin": [ { "gen": { "height": 1301521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4c02cb5326c0efda4fd43eb4c6929a0c2800ddab66ef63b60f19bd22f3c18a" } } ], "extra": [ 1, 6, 125, 122, 72, 129, 19, 65, 229, 103, 51, 226, 152, 143, 42, 70, 88, 109, 71, 94, 74, 119, 186, 112, 157, 68, 148, 184, 93, 102, 138, 228, 160, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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