Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddba8afabe0fcb9c6811dfa1e1307b2f33493352ec391dac529765a04b30395a

Tx prefix hash: 63708612029cde4835c15d5bcd1d2f18d2d1d21d739aee979386af8fadd92f8b
Tx public key: 2ddd11139fe91b42727fbecc0338ba08d4035fb68ce82d02f530478e08f93200
Timestamp: 1739420991 Timestamp [UTC]: 2025-02-13 04:29:51 Age [y:d:h:m:s]: 00:363:20:08:28
Block: 1218137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257730 RingCT/type: yes/0
Extra: 012ddd11139fe91b42727fbecc0338ba08d4035fb68ce82d02f530478e08f932000211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f98f9e83c858e5eafc287e57f848d9581a36690c1ce94d45803f5e00b6cff3f0 0.000600000000 1704952 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 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": 1218147, "vin": [ { "gen": { "height": 1218137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98f9e83c858e5eafc287e57f848d9581a36690c1ce94d45803f5e00b6cff3f0" } } ], "extra": [ 1, 45, 221, 17, 19, 159, 233, 27, 66, 114, 127, 190, 204, 3, 56, 186, 8, 212, 3, 95, 182, 140, 232, 45, 2, 245, 48, 71, 142, 8, 249, 50, 0, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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