Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e741160017de7a6c5c18d0e2308ec481bb97b1674a1b04bdc2809b682c9e74d

Tx prefix hash: 4e0093f4c72a321a86355e68ed1a315d0baf54d7064b1ee555bf07348d4f80b5
Tx public key: 634155ad3e02472b376f5338f9a66e7ab78df68ff09f4d58379dd947a22b2486
Timestamp: 1745938572 Timestamp [UCT]: 2025-04-29 14:56:12 Age [y:d:h:m:s]: 00:008:06:06:53
Block: 1272093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5890 RingCT/type: yes/0
Extra: 01634155ad3e02472b376f5338f9a66e7ab78df68ff09f4d58379dd947a22b24860211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3718a1e1f74d0411a6a24cd2584ce3ee2a74cd16a811bb91aa84ebf975ecfd7 0.600000000000 1759366 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": 1272103, "vin": [ { "gen": { "height": 1272093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3718a1e1f74d0411a6a24cd2584ce3ee2a74cd16a811bb91aa84ebf975ecfd7" } } ], "extra": [ 1, 99, 65, 85, 173, 62, 2, 71, 43, 55, 111, 83, 56, 249, 166, 110, 122, 183, 141, 246, 143, 240, 159, 77, 88, 55, 157, 217, 71, 162, 43, 36, 134, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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