Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a461cbf3c95c40074485db90cbad164c7863fddab25f5ea94d6daeecfb583490

Tx prefix hash: f6b6940736cc17758d449a5bb5924de404d02ad0b8e40f694a56ec7197a2a1e6
Tx public key: a781abe6bdf1851637737d6b4ccf6ae96cea259d91c227d8612210121ac2038f
Timestamp: 1720091426 Timestamp [UTC]: 2024-07-04 11:10:26 Age [y:d:h:m:s]: 01:311:23:04:50
Block: 1058309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473727 RingCT/type: yes/0
Extra: 01a781abe6bdf1851637737d6b4ccf6ae96cea259d91c227d8612210121ac2038f0211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cac04c5df3174b2c2f4f2e3cf1670a044fc0e3fdfa81e397616fbcec3fcc78c4 0.000600000000 1528758 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": 1058319, "vin": [ { "gen": { "height": 1058309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cac04c5df3174b2c2f4f2e3cf1670a044fc0e3fdfa81e397616fbcec3fcc78c4" } } ], "extra": [ 1, 167, 129, 171, 230, 189, 241, 133, 22, 55, 115, 125, 107, 76, 207, 106, 233, 108, 234, 37, 157, 145, 194, 39, 216, 97, 34, 16, 18, 26, 194, 3, 143, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: