Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481a34569fcbc6201ba9d54410fe5f6dae2c74bd813b26115299dfe65e8693b0

Tx prefix hash: 8e74944aa4949ee83d732d2c03e741c2f33ccd00f8f8c61b604276714217c726
Tx public key: 980837804dacfc7abeeac4d59e6d0af810a847f77bdbf462c27f948360da225b
Timestamp: 1748191092 Timestamp [UTC]: 2025-05-25 16:38:12 Age [y:d:h:m:s]: 00:351:04:10:09
Block: 1290746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240792 RingCT/type: yes/0
Extra: 01980837804dacfc7abeeac4d59e6d0af810a847f77bdbf462c27f948360da225b02110000000b1f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8740f6ef98671acf1b74f653e15f637776470b26bbc78e712cf46c80d4b8ff5f 0.000600000000 1778217 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": 1290756, "vin": [ { "gen": { "height": 1290746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8740f6ef98671acf1b74f653e15f637776470b26bbc78e712cf46c80d4b8ff5f" } } ], "extra": [ 1, 152, 8, 55, 128, 77, 172, 252, 122, 190, 234, 196, 213, 158, 109, 10, 248, 16, 168, 71, 247, 123, 219, 244, 98, 194, 127, 148, 131, 96, 218, 34, 91, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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: