Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f2c7e5eb964e579576465233d6b093468f8fdca0f00826390635fc7df9b830

Tx prefix hash: aa4cb7cbdd8920f2664e49fea87dd6f2eeb9f0332c39c68ef669bd1147a903ee
Tx public key: 874e1891a2fb5d0f26fe3d4d6f800a4f9b15e201fe2be1b0a9ca3022555c7e38
Timestamp: 1740382299 Timestamp [UTC]: 2025-02-24 07:31:39 Age [y:d:h:m:s]: 01:078:00:41:30
Block: 1226066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306652 RingCT/type: yes/0
Extra: 01874e1891a2fb5d0f26fe3d4d6f800a4f9b15e201fe2be1b0a9ca3022555c7e38021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b4d76f34eaed04493700d1d3791dabd3ee588cb105fa8d81b54d63511ccdb70d 0.000600000000 1712937 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": 1226076, "vin": [ { "gen": { "height": 1226066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d76f34eaed04493700d1d3791dabd3ee588cb105fa8d81b54d63511ccdb70d" } } ], "extra": [ 1, 135, 78, 24, 145, 162, 251, 93, 15, 38, 254, 61, 77, 111, 128, 10, 79, 155, 21, 226, 1, 254, 43, 225, 176, 169, 202, 48, 34, 85, 92, 126, 56, 2, 17, 0, 0, 0, 2, 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: