Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf0f9728e0d8fd7d3b3fc14509a51a0fcdb4d00cac743564f9525c5eb6d1cc9

Tx prefix hash: 39ae7482fa62a8a490e8bd84a67f43379c67c6d9f40c55dbcc5cef3f5b8d183d
Tx public key: 0f1ddf8173357253fcbdbbfd49e343466f8e3f88aff84e2563f438f31000c780
Timestamp: 1744434269 Timestamp [UTC]: 2025-04-12 05:04:29 Age [y:d:h:m:s]: 01:028:00:40:07
Block: 1259623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271260 RingCT/type: yes/0
Extra: 010f1ddf8173357253fcbdbbfd49e343466f8e3f88aff84e2563f438f31000c7800211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08b7a44ff2fe7e5fb1dc67b55ef15b340ea14c903c7c044c91584fd0c1948b74 0.000600000000 1746772 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": 1259633, "vin": [ { "gen": { "height": 1259623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b7a44ff2fe7e5fb1dc67b55ef15b340ea14c903c7c044c91584fd0c1948b74" } } ], "extra": [ 1, 15, 29, 223, 129, 115, 53, 114, 83, 252, 189, 187, 253, 73, 227, 67, 70, 111, 142, 63, 136, 175, 248, 78, 37, 99, 244, 56, 243, 16, 0, 199, 128, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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) | monero version: