Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8117758e70afba25c9909c000a6f225ba5db7f2e8f1133457c781482485ad35

Tx prefix hash: a416417ea31f78b65c1d94c096661a0d61dac604820806ed62fb4133f26e1036
Tx public key: 4ca3eeb328c9f9f7aafd03f7ec12dc62c26469b3a933b18bf1ec1e253dfd38ca
Timestamp: 1749900234 Timestamp [UCT]: 2025-06-14 11:23:54 Age [y:d:h:m:s]: 00:160:05:31:48
Block: 1304801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112278 RingCT/type: yes/0
Extra: 014ca3eeb328c9f9f7aafd03f7ec12dc62c26469b3a933b18bf1ec1e253dfd38ca02110000000cbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f8d2c367ab964ead5cffbc6fb4b0391a5b9edbdbb61ac11c9b3ce5343f3b1e 0.600000000000 1792394 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": 1304811, "vin": [ { "gen": { "height": 1304801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f8d2c367ab964ead5cffbc6fb4b0391a5b9edbdbb61ac11c9b3ce5343f3b1e" } } ], "extra": [ 1, 76, 163, 238, 179, 40, 201, 249, 247, 170, 253, 3, 247, 236, 18, 220, 98, 194, 100, 105, 179, 169, 51, 177, 139, 241, 236, 30, 37, 61, 253, 56, 202, 2, 17, 0, 0, 0, 12, 191, 81, 178, 162, 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