Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05ce40ca6bb37639a29d1966578f86d383e2e659430eba27fa2ba9918776b57d

Tx prefix hash: d51efb08d4d3d6e561c4720c81b608d29bb0d8f7735171cbcb7a043ca9e14c89
Tx public key: 0b6480841f5a77e9ffd0123e591be66d882438eaafa4218c8fd8a6e79794d277
Timestamp: 1741462656 Timestamp [UTC]: 2025-03-08 19:37:36 Age [y:d:h:m:s]: 01:062:20:39:12
Block: 1235037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296159 RingCT/type: yes/0
Extra: 010b6480841f5a77e9ffd0123e591be66d882438eaafa4218c8fd8a6e79794d277021100000016007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e35f2c8a6e289e9241b37b7a226e93af1c650a406a47992163ec6e9320980474 0.000600000000 1721972 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": 1235047, "vin": [ { "gen": { "height": 1235037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35f2c8a6e289e9241b37b7a226e93af1c650a406a47992163ec6e9320980474" } } ], "extra": [ 1, 11, 100, 128, 132, 31, 90, 119, 233, 255, 208, 18, 62, 89, 27, 230, 109, 136, 36, 56, 234, 175, 164, 33, 140, 143, 216, 166, 231, 151, 148, 210, 119, 2, 17, 0, 0, 0, 22, 0, 127, 151, 138, 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: