Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 447925639e4446da2b24042544aefb7a0279ee94b709fd6b2d96a2edf7be41a1

Tx prefix hash: 7bab716213ee409d3c19be1155c18e27d99672ce36be1f894317e0967e3310bb
Tx public key: f88bebbb1414eaea74ac2ea8896862544cd6a77e67b1ddd53a305721ba334743
Timestamp: 1711402835 Timestamp [UTC]: 2024-03-25 21:40:35 Age [y:d:h:m:s]: 02:237:17:11:38
Block: 986302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694891 RingCT/type: yes/0
Extra: 01f88bebbb1414eaea74ac2ea8896862544cd6a77e67b1ddd53a305721ba33474302110000000b59dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8355dacb00e29e65dff81a9db7d5229a1da193b71a6c71e098460812fb86f30d 0.000600000000 1446531 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": 986312, "vin": [ { "gen": { "height": 986302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8355dacb00e29e65dff81a9db7d5229a1da193b71a6c71e098460812fb86f30d" } } ], "extra": [ 1, 248, 139, 235, 187, 20, 20, 234, 234, 116, 172, 46, 168, 137, 104, 98, 84, 76, 214, 167, 126, 103, 177, 221, 213, 58, 48, 87, 33, 186, 51, 71, 67, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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: