Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2c2c1a6b87f25e7089afd061b6769557714c3ce7d80aec6de31fbe626b2da8

Tx prefix hash: 78cfa928fa1d39eabff0eed264c6bff3c4461e9fa6fe73dc982505f5d0d2c366
Tx public key: 768d1a5e1229950e4e24518844b7e5e10229db074e467924acc1fe3553c33bc3
Timestamp: 1627633466 Timestamp [UTC]: 2021-07-30 08:24:26 Age [y:d:h:m:s]: 04:215:04:13:46
Block: 303738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184614 RingCT/type: yes/0
Extra: 01768d1a5e1229950e4e24518844b7e5e10229db074e467924acc1fe3553c33bc302110000001a282c04e2000000000000000000

1 output(s) for total of 0.060477022810 xmr

stealth address amount amount idx tag
00: 508613f84cbddd25307c41be1254361e74389405ae615c47e1f2615f4f382dbc 0.060477022810 633913 of 0 -

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 dinastycoin-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": 303748, "vin": [ { "gen": { "height": 303738 } } ], "vout": [ { "amount": 60477022810, "target": { "key": "508613f84cbddd25307c41be1254361e74389405ae615c47e1f2615f4f382dbc" } } ], "extra": [ 1, 118, 141, 26, 94, 18, 41, 149, 14, 78, 36, 81, 136, 68, 183, 229, 225, 2, 41, 219, 7, 78, 70, 121, 36, 172, 193, 254, 53, 83, 195, 59, 195, 2, 17, 0, 0, 0, 26, 40, 44, 4, 226, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369