Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17ddb4c436bfe2602e568077b5014e89cee67e79501c7396049baf07484646e

Tx prefix hash: b9da987f6957c960da29f59d4746a627c9206d55c4fb68432904a3ff67bfe41d
Tx public key: 022b0cdb0a3817322b1e19cd14338bfc6e2615d309d88c33d8d2515178512986
Timestamp: 1743960152 Timestamp [UTC]: 2025-04-06 17:22:32 Age [y:d:h:m:s]: 01:141:23:30:22
Block: 1255688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365860 RingCT/type: yes/0
Extra: 01022b0cdb0a3817322b1e19cd14338bfc6e2615d309d88c33d8d25151785129860211000000056c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c34c63c7d7cf04b8ced999cb662ec67a2e075b11c594c5e5048849063a9c51b 0.000600000000 1742793 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": 1255698, "vin": [ { "gen": { "height": 1255688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c34c63c7d7cf04b8ced999cb662ec67a2e075b11c594c5e5048849063a9c51b" } } ], "extra": [ 1, 2, 43, 12, 219, 10, 56, 23, 50, 43, 30, 25, 205, 20, 51, 139, 252, 110, 38, 21, 211, 9, 216, 140, 51, 216, 210, 81, 81, 120, 81, 41, 134, 2, 17, 0, 0, 0, 5, 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: