Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d1bd84d692a058520bb89ed8e763626c06283b0ff963aafff47bf8f9b51d2b3

Tx prefix hash: 959518e253429303ddbb85beede541556de9e46fb28c5c9ed21bb663b7567f1b
Tx public key: 0a50621c1d080300f47e6d4727a94e485528e1f4b11440864198ddc26a3a746a
Timestamp: 1739053246 Timestamp [UTC]: 2025-02-08 22:20:46 Age [y:d:h:m:s]: 01:285:02:17:36
Block: 1215084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467960 RingCT/type: yes/0
Extra: 010a50621c1d080300f47e6d4727a94e485528e1f4b11440864198ddc26a3a746a021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3fb2cd46ffb938b07e1240e4fa1d26ea495491a7cf56ffa3bc078b6a0084539c 0.000600000000 1701881 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": 1215094, "vin": [ { "gen": { "height": 1215084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fb2cd46ffb938b07e1240e4fa1d26ea495491a7cf56ffa3bc078b6a0084539c" } } ], "extra": [ 1, 10, 80, 98, 28, 29, 8, 3, 0, 244, 126, 109, 71, 39, 169, 78, 72, 85, 40, 225, 244, 177, 20, 64, 134, 65, 152, 221, 194, 106, 58, 116, 106, 2, 17, 0, 0, 0, 1, 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: