Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76de4f910e2f1c58054f6487421156ebbe8918bf86332c99cfa36ba4dbdb85b

Tx prefix hash: 041522119f5675eb18bebd4fddc06a94b074ae9e60d4513af3d2563f71d46817
Tx public key: 48cec651a5c2ec9ebd3c7f8d1f87fed2653e6444a20ca69525d3f372ede70754
Timestamp: 1728005425 Timestamp [UTC]: 2024-10-04 01:30:25 Age [y:d:h:m:s]: 02:045:19:29:53
Block: 1123927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557452 RingCT/type: yes/0
Extra: 0148cec651a5c2ec9ebd3c7f8d1f87fed2653e6444a20ca69525d3f372ede7075402110000000491e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd84aa2fb1389c164aaa43e748b445c709f6ec043997c6f5a85edb6cab970517 0.000600000000 1606476 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": 1123937, "vin": [ { "gen": { "height": 1123927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd84aa2fb1389c164aaa43e748b445c709f6ec043997c6f5a85edb6cab970517" } } ], "extra": [ 1, 72, 206, 198, 81, 165, 194, 236, 158, 189, 60, 127, 141, 31, 135, 254, 210, 101, 62, 100, 68, 162, 12, 166, 149, 37, 211, 243, 114, 237, 231, 7, 84, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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: